-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Conversation
Elasticsearch upgrade test is failling on K8S 1.16 because Elasticsearch chart version < 7.4.0 used Elasticsearch upgrade test first install a 7.0.0-alpha1 chart, then upgrade it to last version. Adding tests and support for K8S 1.16 requires that we update the upgrade test to check 7.4.0 to latest version upgrade instead of 7.0.0-alpha1 to latest version upgrade. Eventually we could change the test only for K8S 1.16:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Makefile changes look good to me, but I had a couple of suggestions.
Co-authored-by: Aaron Bull Schaefer <aaron@elasticdog.com>
@@ -40,3 +40,4 @@ APM_SERVER_SUITE: | |||
KUBERNETES_VERSION: | |||
- '1.14' | |||
- '1.15' | |||
- '1.16' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish we could define the chart versions for upgrade testing here somehow so it is very clear what the test cases are, something like this
- kubernetes_version: '1.14'
upgrade_from_chart_version: '7.0.0-alpha1'
- kubernetes_version: '1.15'
upgrade_from_chart_version: '7.0.0-alpha1'
- kubernetes_version: '1.16'
upgrade_from_chart_version: '7.4.0'
But I think we can only fit this logic into the jenkins job inline shell script, or the Makefile inline shell script the way the job axes work, so adding into the Makefile makes sense to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I have concerns about the lack of error handling in the new shell snippets, but those could be addressed in another PR, the logic will work in the happy-path and get us testing on 1.16.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jenkins test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* add CI tests for GKE 1.16 * add jq to Docker image
* add CI tests for GKE 1.16 * test Elasticsearch upgrade from 7.4.0 on K8S 1.16 due to previous version of Elasticsearch chart not compatible with K8S 1.16 (see #635 (comment)) * move Elasticsearch upgrade test logic to dedicated shell script to improve error handling * add jq to Docker image
* add CI tests for GKE 1.16 * test Elasticsearch upgrade from 7.4.0 on K8S 1.16 due to previous version of Elasticsearch chart not compatible with K8S 1.16 (see #635 (comment)) * move Elasticsearch upgrade test logic to dedicated shell script to improve error handling * add jq to Docker image
backported to |
This PR add tests on K8S 1.16 using GKE